-
Notifications
You must be signed in to change notification settings - Fork 631
[rush-pnpm] Fix rush-pnpm patch-commit command #4874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@iclanton Pete is on vacation. We need your help with the review and merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@L-Qun have you validated that this still works in non-subspaces scenarios (or I guess, the default subspace)?
common/changes/@microsoft/rush/fix-pnpm-patch_2024-08-09-10-38.json
Outdated
Show resolved
Hide resolved
Head branch was pushed to by a user without write access
….json Co-authored-by: Ian Clanton-Thuon <iclanton@users.noreply.github.com>
@iclanton Could you help to publish a new rush version |
@L-Qun Published in Rush v5.131.3 |
@L-Qun - Looks like this PR introduced a breaking change. In the non-subspaces scenario, the patches folder is now |
Details
After upgrading the rush version(5.131.0) in tiktok monorepo, we encountered an error when running
rush-pnpm --subspace subspaceName patch-commit xxxx
After taking a close look at the rush source code, I found that the path to the folder related to the pnpm patches was incorrect. Therefore, I fixed this issue in that MR
How it was tested
To test the implementation, the following commands were executed:
rush install -t .
rush-pnpm --subspace subspaceName patch xxx
rush-pnpm --subspace subspaceName patch-commit xxx
No errors were encountered.
Impacted documentation
None